From: | Paul Hill |
Date: | 7 Sep 2001 at 20:35:25 |
Subject: | Re: [amiga-c] VB int problem (was Re: Help needed with random crashing problem) |
On 07-Sep-01 16:19:49, Paul Qureshi wrote:
>Hi guys.
>Well, I tracked down the problem to my vertical blank interrupt. I can't
>figure it out though, so I'm going to rewrite it in assembler or find
>another way to do volume control.
>Anyone got any ideas why a vb int written in Storm C might fail? I have
>__interrupt and __saveds, and I return(0) at the end too.
What version of StormC are you useing?
>To answer Paul Hills questions:
>> Have you tried putting lots of debug statements in the code?
>Yeah, I have. Unfortunatly, they didn't help much, as it was the
>interrupt that was causing the problem.
>> I normally stick tons of kprintf()s in the code until I've narrowed it
>> down to where the fault is. This way I can use either Sushi or a
>> serial terminal to monitor what's going on. kprintf is in debug.lib
>> BTW.
>I was just using printf() since the program uses the serial port and
>there is no stdio output anyway.
But you can't call printf() from an interrupt. You can however call
kprintf().
Also, use Sushi to catch the debug output.
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Secure your servers with 128-bit SSL encryption! Grab your copy of VeriSign's FREE Guide: "Securing Your Web Site for Business." Get it Now!
http://us.click.yahoo.com/n7RbFC/zhwCAA/yigFAA/dpFolB/TM
---------------------------------------------------------------------~->
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/